home *** CD-ROM | disk | FTP | other *** search
- Path: atlas.de!usenet
- From: khd@nano.atlas.de (Karl-Heinz Dewenter)
- Newsgroups: comp.edu,comp.lang.c,comp.lang.c++
- Subject: Re: C or C++ for a 14-year old?
- Date: 16 Jan 1996 15:01:04 GMT
- Organization: Atlas Elektronik GmbH
- Message-ID: <KHD.96Jan16160104@nano.atlas.de>
- References: <4b30ld$lp2$1@mhafc.production.compuserve.com>
- <4d4jeh$fv1@wombat.melbpc.org.au>
- <w+PJjMD4ED1aLz3@dexam.another.gun.de> <4ddsg4$p4e@sundog.tiac.net>
- NNTP-Posting-Host: nano.atlas.de
- In-reply-to: amoreira@nine.com's message of Mon, 15 Jan 1996 15:42:33 GMT
-
- In article <4ddsg4$p4e@sundog.tiac.net> amoreira@nine.com (Alberto C Moreira) writes:
-
- ...>
- > Still, there's no worse restriction on a programmer than not to be
- > able to talk directly to the hardware.
-
- Most programmers don't want "to talk directly to the hardware" because that
- restricts the program to only one platform (or in worst case to only
- _one_ single machine).
- And there will be more than Intel based PCs in near future, I hope.
- So this is a very good restriction, if you got a good library & os.
-
- >
- > The best operating system isn't the one that does more, but the one
- > that gets out of the way when it's not needed. With DOS, I can
- > reach my hardware any time I want. With Windows, I can do that by
- > writing a VDD. With Windows 95, I can load that VDD on the fly.
- >
- > With Unix, I probably need to recompile the kernel - that is, if I'm a
- > hacker and I have the Unix source code.
- >
-
- So, if anyone is a hardware-hacker, he should prefer LINUX. He can modify the
- kernel and so talk *in*directly to the hardware from his own program through
- his own drivers.
- - Or, if he loves Bill Gates, he should perhaps use Win95, writing VDDs.
- Programs talking directly to the hardware without any driver interface are aweful
- and anachronistic.
-
- Karl-Heinz Dewenter
- khd@jekyll.atlas.de
-
- That's only my pesonal opinion, not preventing it to be true ;-o
-